


<h2>



December 2000 JUG Meeting</h2>



&nbsp;



<center><table BORDER CELLSPACING="4" CELLPADDING="3" WIDTH="61%">



<tr>



<td VALIGN="CENTER" BGCOLOR="#6699FF">



<center>



<h3>



Triangle Java Users Group Presents:</h3></center>







<center><font size="+2">Towards Resolving Architectural Forces in Component-based Software



</font>



<br>&nbsp;



<p><b>presented by</b>



<p><b>Toby Sarver</b>

<p><b>HAHT Commerce</b>





<p>Monday, December 18, 2000&nbsp;



<br>6:30 PM - 9:00 PM&nbsp;



<p>LOCATION: MCNC Auditorium&nbsp;



<br>3021 Cornwallis Road&nbsp;



<br>Research Triangle Park, North Carolina&nbsp;



<p>919.248.1800&nbsp;</center>



</td>



</tr>



</table></center>







<hr ALIGN="CENTER">



<br><font size="+1">Abstract:</font>



<dir><font size="-1">

Component-based software has been touted in the industry as the next

great paradigm for delivering software.

Yet there is no clear definition of what

makes something a component, nor what capabilities a component framework

should include.

This presentation will briefly compare and contrast

COM, ActiveX, Java Beans, EJB, and CORBA to get an understanding

for some of the common concepts and motivating forces in component

frameworks.

Then we will attempt to provide a definition for "component"

and "component framework" that is broad enough to encompass the

industry examples.

Finally, we will see how HAHT Commerce delivers its products using

component-based software techniques, and what architectural forces

exist and how they are resolved.

</font></dir>



<!-- No objectives this time

<br><font size="+1">Objectives:</font>



<dir><font size="-1">

<p>Attendees should come away with an understanding of: </p>

<UL>

<LI>X</LI>

<LI>Y</LI>

<LI>Z</LI>

</UL>

No objectives this time -->



</font></dir>



<br><font size="+1">Format:</font>



<dir><font size="-1">

The talk will last about 60 minutes (Q&A will follow)

</font></dir>



<br><font size="+1">Brief biography of presenter:</font>



<dir><font size="-1">

<br>

Toby Sarver has been working with object technology since 1987,

including Java, Smalltalk, C++, OO software engineering (SDLC and

processes), and patterns.

He has worked with Fortune 100 companies to adopt and

leverage object technology.

He currently architects HAHT Commerce's e-Scenarios.

HAHT Commerce helps click-and-mortar companies succeed in B2B

sell-side e-commerce.  Their e-Scenarios are e-commerce applications

that inter-operate with ERP systems.

Mr. Sarver was a recent panelist at

OOPSLA 2000, and has participated in many OOPSLA workshops in the

areas of patterns and architecture

(e.g., large, distributed systems, components, etc.).

</font></dir>



<hr ALIGN="CENTER">



<h3>



AGENDA:</h3>

6:30 pm - Meet, talk, snacks
<br>7:00-7:15 - Announcements, Status of JUG projects
<br>7:15 - 8:15 - Presentation
<br>8:15 - 8:30 -  Discussion with presenter
<br>8:30 - 9:00 -  Election of the 2001 JUG Board
<br>9:00 - Doors close


<hr ALIGN="CENTER">



<h3>



DIRECTIONS to MCNC:</h3>



<b>From Raleigh:</b>



<br>Take I-40 West toward Durham and Chapel Hill. You will enter RTP. Where



I-40 splits, bear right onto the Durham Freeway North (Highway 147). Take



the Cornwallis Road Exit. At the end of the exit ramp, bear right - cross



back over the Freeway. MCNC is located approximately 3/4 mile on the right.



<p><b>From Durham:</b>



<br>Get on the Durham Freeway South (Highway 147). Take the Cornwallis



Road exit. At the end of the ramp, bear right - MCNC is approximately 3/4



mile on right.



<p>Click here for <a href="http://trijug.org/mcnc/?/directions.html">map with



directions</a>, or visit the <a href="http://trijug.org/mcnc/?/gotomcnc.html">MCNC



web site</a>.



<p>






